I did end up starting a sort of web codey-type of project recently. I’m not using tilde.club for it at all, but I figured I’d jot down a word or two about it.
I’ve got this old blog over on blogger. Remember blogger? This was a blog I started for one purpose only: to write down solutions for IT problems I encountered, so other people could turn up those solutions when googling for help. Turns out some of those posts get a lot of hits from search engines. And because blogger made it easy and because I didn’t particularly care about beautiful design on this ugly, single-purpose site, I turned on AdSense ads. And now that stupid blog is the only web property of mine that ever created any income. Even now, on average, about $10 USD trickles in via ad clicks every month. Not a lot, certainly, but it helps defray/justify hosting costs for my other domains.
I decided to move this thing on to my own domain and use Kirby for the CMS, just to try something new. Kirby uses plain text files (Markdown-style) as the source for each post. Well, I had been cutting and pasting every post into a new text file, and it involved a lot of clicking around, when I thought, why not write some code. I mean, it will probably take me longer to do the same job but it will be more educational.
So that’s my project. I’m writing a Python script to convert the huge XML export file (thanks for that much, Blogger) into a tidy collection of text files, containing correct date-stamps, tags, and maybe even comments if I get that far. I’m so out of shape, and I don’t actually know Python, so I have. to. Google. Every. Single. Step. How do strings work in Python? How to use for
loops? How to parse XML, or interpret an RFC3339 timestamp?
And in the process I have to install a new library, which means figuring out how to do that from a Github source, which means installing Homebrew so as to install a more up-to-date version of Python which includes the pip
command for installing libraries. But apparently I already have Homebrew installed, but it’s not working because it’s using the wrong Ruby interpreter (solved thanks to this). But once I got that cleared up I was able to implement fixes and unwind my stack all the way back up to solving the original problem.
Part of me enjoys this kind of thing, gets hooked on it. But another (very big) part of me loathes it, because it wants the computer to make things simpler, not more complicated; it knows that my time and energies are limited, and divided among several pursuits and people, and that I don’t have time for this.
RELATED: Four years ago I wrote a post titled The Voodoo Veil about working with computers.
#